Restore a Legacy BIOS/MBR TIB Backup with Acronis True Image

To restore a legacy BIOS/MBR Windows system from a .tib backup, use compatible Acronis True Image recovery media, select the required system partitions, and map them carefully to the destination disk. This process restores a backup; it is often called “ghosting,” but it is not Norton Ghost's GHO format.

Recovery overwrites the selected destination. Back up newer files before proceeding. Use a backup you trust, preferably one you created yourself, and keep it on a separate drive from the destination.

Check compatibility before recovery

• Confirm the backup was made for the system and disk layout you intend to restore.
• Check that your Acronis version can read the archive.
• Identify whether the backup uses legacy BIOS/MBR or UEFI/GPT boot.
• Make sure the target hardware supports the required boot mode and storage drivers.
• Keep Windows licensing details and encryption recovery keys available.

Do not switch a working UEFI installation to legacy mode merely because an old tutorial uses it. Some modern systems do not support legacy boot at all. See the firmware-mode guide and the separate TIB and UEFI/GPT recovery overview.

A TIB extension does not determine recovery speed or guarantee bootability. Likewise, restoring or reinstalling does not automatically erase a digital Windows license, though activation can be affected by edition or hardware changes.

1. Start a compatible recovery environment

Boot trusted recovery media and open Acronis True Image. Confirm that both the backup drive and destination disk are visible. The screenshots below show an older interface; labels can vary.

2. Select the backup archive

Open Recovery > Disk and Partition Recovery, then browse to the TIB file.

Select the intended backup and recovery point. Check its date and contents rather than choosing solely by its filename. Use the available validation function if appropriate before overwriting the destination.

3. Choose the disk and partitions to recover

Select Recover whole disks and partitions for system-image recovery. Review the components in the archive. A legacy Windows system may need a separate boot/system partition as well as the Windows partition.

Recovering an entire disk and recovering only selected partitions have different effects. Whole-disk recovery can replace the destination layout and include boot records. Select what your recovery plan requires; do not tick every item simply because a screenshot does.

4. Map each item to its destination

Use New location to choose the intended destination for the selected partition. Identify the physical disk by model and capacity and compare its existing layout.

Do not rely on the letter C: alone. Drive letters in a rescue environment can differ from normal Windows. Check partition size, contents where accessible, and the disk it belongs to. Cancel if the mapping would overwrite a data partition you need.

Review each partition's location and size, then continue through the remaining mapping pages. If the wizard includes an MBR or other boot-record choice, check its target disk separately.

5. Review the summary and restore

Read the operation summary before clicking Proceed. Confirm the archive, recovery point, source partitions, destination disk, and any partitions to be replaced. An unrelated data disk should not appear as a write destination.

Keep the system powered and the archive drive connected until recovery completes. Duration varies with the archive, compression, and storage hardware.

6. Test startup and check the restored system

When recovery succeeds, exit the recovery environment and restart from the restored disk in the boot mode appropriate for that image. A successful restore message confirms the recovery operation, not that every driver, application, or activation state is correct.

Check that Windows starts, your expected files are present, and the required devices work. If restoring to different hardware, additional drivers or a supported migration procedure may be needed.

If Windows does not start

• Confirm that firmware is selecting the restored disk in the correct mode.
• Check whether the backup included every required boot partition.
• Review the destination mappings rather than immediately restoring again.
• Check archive compatibility and consult documentation for your Acronis version.

The current Acronis system-recovery guide provides additional recovery context. Do not repeatedly change firmware or rewrite boot records without identifying the mismatch first.